Virtual repository management

ABSTRACT

Virtual repository management is disclosed. An indication is received that a content management functionality is desired to be available with respect to one or more external content items. A reference object is created for each for the one or more external content items that represents the external content item and enables the content management functionality to be performed with respect to the external content item.

CROSS REFERENCE TO OTHER APPLICATIONS

This application is a continuation of co-pending U.S. patent applicationSer. No. 13/189,230, entitled VIRTUAL REPOSITORY MANAGEMENT filed Jul.22, 2011 which is incorporated herein by reference for all purposes,which is a continuation of U.S. patent application Ser. No. 11/355,556,now U.S. Pat. No. 8,015,222, entitled VIRTUAL REPOSITORY MANAGEMENTfiled Feb. 16, 2006 which is incorporated herein by reference for allpurposes, which claims priority to U.S. Provisional Application No.60/729,987, entitled VIRTUAL REPOSITORY MANAGEMENT filed Oct. 24, 2005which is incorporated herein by reference for all purposes. U.S. patentapplication Ser. No. 11/355,556 also claims priority to U.S. ProvisionalApplication No. 60/764,896, entitled VIRTUAL REPOSITORY MANAGEMENT TOPROVIDE RETENTION MANAGEMENT SERVICES filed Feb. 3, 2006 which isincorporated herein by reference for all purposes.

BACKGROUND OF THE INVENTION

Information can be stored or managed by systems designed to helporganize, manage, or otherwise provide useful functionality to the useror owner of the information. In some cases, an owner of information canhave multiple systems that are managing or storing information that theowner desires to be able to control or manage in a similar, uniform,consistent, and/or verifiable manner. This can be especially true fordocuments that need to be retained or disposed for regulatory purposes.For example, financial, corporate, litigation, medical, personnel, andsecurities information may all have requirements that an owner wouldwant to meet for information in all of the systems that the owner hasinformation stored in or managed by. However, the multiple systems maynot be able to be controlled or managed natively in a similar or uniformmanner. One approach to this problem has been to migrate content to acommon platform, such as a common content management system, but in manycases such migration is time consuming and otherwise costly, given thevast amounts of data held and/or produced by some enterprises, forexample, and migration does not enable owners of data to take advantageof useful life and/or desirable characteristics and/or nativefunctionality of legacy systems. It would be beneficial to be able tocontrol or manage multiple systems with different characteristics in asimilar or uniform manner.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the invention are disclosed in the followingdetailed description and the accompanying drawings.

FIG. 1 is a block diagram illustrating an embodiment of a system forvirtually managing repositories.

FIG. 2 is a block diagram illustrating an embodiment of referenceobjects referring to external content.

FIG. 3 is a flow diagram illustrating an embodiment of a process forvirtual repository management.

FIG. 4 is a flow diagram illustrating an embodiment of a process forvirtual repository management.

FIG. 5 is a flow diagram illustrating an embodiment of a process forvirtual repository management.

FIG. 6 is a flow diagram illustrating an embodiment of a process forfinding objects of interest for virtual repository management.

FIG. 7 is a flow diagram illustrating an embodiment of a process forvirtual repository management.

FIG. 8 is a flow diagram illustrating an embodiment of a process forperforming an operation with respect to content stored in an externalrepository under virtual management.

DETAILED DESCRIPTION

The invention can be implemented in numerous ways, including as aprocess, an apparatus, a system, a composition of matter, a computerreadable medium such as a computer readable storage medium or a computernetwork wherein program instructions are sent over optical or electroniccommunication links. In this specification, these implementations, orany other form that the invention may take, may be referred to astechniques. A component such as a processor or a memory described asbeing configured to perform a task includes both a general componentthat is temporarily configured to perform the task at a given time or aspecific component that is manufactured to perform the task. In general,the order of the steps of disclosed processes may be altered within thescope of the invention.

A detailed description of one or more embodiments of the invention isprovided below along with accompanying figures that illustrate theprinciples of the invention. The invention is described in connectionwith such embodiments, but the invention is not limited to anyembodiment. The scope of the invention is limited only by the claims andthe invention encompasses numerous alternatives, modifications andequivalents. Numerous specific details are set forth in the followingdescription in order to provide a thorough understanding of theinvention. These details are provided for the purpose of example and theinvention may be practiced according to the claims without some or allof these specific details. For the purpose of clarity, technicalmaterial that is known in the technical fields related to the inventionhas not been described in detail so that the invention is notunnecessarily obscured.

Virtual repository management is disclosed. An indication is receivedthat a content management functionality is desired to be availableand/or performed with respect to one or more external content items. Asused herein, the term “external content item” refers to a content item,such as a file or other stored item, that is not ingested by and broughtunder direct control of a content management system and/or other systemor application that is being used and/or configured to perform one ormore content management functions with respect to the content item.Examples of external content items include files and other items managedby a “legacy” (for example, an older version of a content managementsystem) or other content management system that is of a different type,e.g., from a different vendor or designed for a purpose other thancontent management (for example, customer relations management), than acontent management system or application that is being used to provideone or more content management functions with respect to items stored inand managed by the legacy or other system. For each of at least a subsetof the one or more external content items a reference object is createdthat represents the external item and enables the content managementfunctionality to be performed with respect to the external content item.In various embodiments, the content management functionality isretention management, business process management, customer relations,or security management.

FIG. 1 is a block diagram illustrating an embodiment of a system forvirtually managing repositories. In the example shown, contentmanagement system 100 is coupled to content system 120 and one or moreuser systems, which are represented in FIG. 1 by the personal computeror workstation 101. In various embodiments, content management system100 is coupled to content system 120 and one or more user systems usinga local network, a wide area network, the Internet, a wired network, awireless network, or a direct connection. In some embodiments, users arecoupled or connected to a system that is in turn coupled or connected tocontent management system 100 via network or direct connections. Contentmanagement system 100 is also coupled to one or more external contentsystems, represented in FIG. 1 by legacy content systems 114, 116, 118,and 119. In some embodiments, an external content system comprises asystem with associated content that has not been ingested into contentmanagement system 100 where the ingestion of content comprises takingthe associated content under direct management and control of contentmanagement system 100. In various embodiments, a legacy or otherexternal content system comprises an enterprise content management (ECM)system, an enterprise resource planning (ERP) system, a customerrelations management (CRM) system, a business process management (BPM)system, different version of a system (for example, an older version ofcontent management system 100), enterprise content integration (ECI)system, or enterprise application integration (EAI) system. In someembodiments, external content systems that are not “legacy” contentsystems, i.e., not an older system that is being managed by a newercontent management system 100, are managed virtually as describedherein. In some embodiments, a legacy or other external content systemincludes a content server, metadata, and a content store similar tocontent system 120. In some embodiments, a legacy or other externalcontent system comprises a data repository.

In the example shown in FIG. 1, content management system 100 includesapplication 102, content management framework 104, and adapters 106. Oneor more user systems interact with application 102 in order to make useof content management system functionality (for example, businessprocess management, retention management, security management, etc.). Invarious embodiments, application 102 interacts with content managementframework 104 that enables access to information or content that isstored in legacy content systems 114, 116, 118, and 119 and/or contentsystem 120 or enables the application to store information to legacycontent systems 114, 116, 118, and 119 and/or content system 120. Tointeract with legacy content systems 114, 116, 118, and 119, contentmanagement framework 104 is coupled to adapters 106. In someembodiments, content management framework 104 comprises foundationobject classes and core operations and logic. Adapters 106 handleinteractions between content management system 100 and legacy systems114, 116, 118, and 119. Adapters 106 include a plurality of adaptersrepresented by 108, 110, and 112. In some embodiments, adapters 108,110, and 112 are specific to a type of legacy or other external contentsystem. For example, a type of customer relations management system, ora series of systems from the same vendor with similar interfacingrequirements, has a corresponding adapter for communication with contentmanagement system 100. In the example shown, the interfacingrequirements for legacy content system 118 and 119 are similar andcontent management system 100 uses adapter 112 to interact with bothlegacy content system 118 and legacy content system 119.

In some embodiments, adapters 106 translate commands from contentmanagement system 100 to the appropriate syntax and format required by atype of legacy or other external content system. In some embodiments,adapters 106 normalize the responses from a given type of legacy orother external content system to the appropriate syntax and formatrequired by content management system 100.

Content system 120 includes content server 122, metadata 124, andcontent store 126. Content server 122 communicates with contentmanagement system 100 and provides stored content and/or metadata whenrequested by and/or via content management system 100 and/or storescontent and/or associated metadata for content received from and/or viacontent management system 100. Metadata 124 contains information relatedto content stored in content store 126. In some embodiments, metadata124 comprises a meta-catalog of content objects with respect to whichone or more content management functions are available to be performedby and/or via content management system 100. In some embodiments, themeta-catalog includes content objects associated with items of contentstored in content store 126 and also reference objects associated withitems of content stored in legacy or other external content systems. Insome embodiments, metadata information in metadata 124 is coupled withcontent stored in content store 126—for example, security or retentioninformation is coupled to content so that the security or retentioninformation are always present and/or utilized for content managementsystem applications.

In various embodiments, content management system 100, content system120, and legacy content systems 114, 116, 118, and 119 are implementedusing one or more hardware units, one or more processing units/devices,one or more storage units/devices, or one or more memory units/devices.

FIG. 2 is a block diagram illustrating an embodiment of referenceobjects referring to external content. In some embodiments, metadata inmeta-catalog 200 is included in metadata 124 of FIG. 1 and content store208 is content store 126. In the example shown, metadata in meta-catalog200 includes content objects 204 that refer to items of content incontent store 208. For example, content objects 204 include in theexample shown in FIG. 2 content objects Cx and Cy which refer to contentitems X and Y, respectively, in content store 208. In variousembodiments, the content objects comprise a location pointer, e.g.,pointing to a location in content store 208 in which a correspondingitem of content is stored, a database row entry, a data structure withinformation such as content title, keywords associated with content,abstract of content, related documents/information, securityinformation, retention information, or rules associated withinformation—e.g., publishing rules with regard to other formats such asHTML, PDF, etc., version control rules, or business process rules. Invarious embodiments, a location pointer is a physical address on astorage device, removable storage media, or in a memory or a logicaladdress that enables access to a location on a storage device, removablestorage media, or in a memory. Metadata in meta-catalog 200 alsoincludes one or more reference objects 202, represented in FIG. 2 by Rz,that refer to content in one or more legacy content systems representedin FIG. 2 by legacy content system 212. In some embodiments, legacycontent system 212 comprises a repository that has not been ingesteddirectly into the content management system so that the information inthe repository is not stored in the content management system and is notcontrolled directly by the content management system. In someembodiments, the legacy content systems are repositories or informationsystems that are not desired to be the central manager of informationheld in multiple systems. In the example shown, legacy content system212 includes one or more items of content represented by Z in contentstore 210. A reference object Rz refers to the content Z in contentstore 210 and as described more fully below enables content managementfunctions to be performed with respect to content item Z by and/or via acontent management system associated with meta-catalog 200. The contentitem Z is represented in a legacy content system metadata 206 by acontent object Cz. In this example, the legacy content system is amanaged content system that, like the content system with whichmeta-catalog 200 and content store 208 are associated, generates andmaintains a set of metadata in which each item of content undermanagement by the legacy content system 212 is represented by a contentobject such as content object Cz. In some embodiments, external contentstored in an external repository to be managed virtually is stored in anexternal repository that is not a managed repository, e.g., a contentserver or file system, such that the external content repository/systemdoes not include an external system metadata such as metadata 206. Insome embodiments, a reference object such as Rz is generated andpopulated at least in part by accessing data comprising and/orassociated with content item Z. In some embodiments, a reference objectsuch as Rz is generated and populated at least in part by accessingmetadata associated with content item Z, such as content object Cz inthe example shown.

FIG. 3 is a flow diagram illustrating an embodiment of a process forvirtual repository management. In the example shown, in 300 anindication is received that a content management functionality isdesired to be available and/or performed with respect to one or moreexternal content items In various embodiments, content managementfunctionality comprises process automation (for example, work flowautomation, life cycle automation, ets.), library services (for example,access control, versioning, encryptions, multiple documentrepresentation handling, etc.), repository services (for example,authentication, backup, distributed storage, etc.), core contentservices (for example search, annotation, rendering to differentformats, linking into a group). In some embodiments, the externalcontent items are in legacy content systems for which it is desired tohave some centrally available management functionality. In someembodiments, virtual repository management of external content held inlegacy content systems enables central management of content without theexpense, difficulty, and/or risk associated with ingesting the contentsof the legacy content system into the central content management system.In some embodiments, an indication that a management functionality isdesired to be available comprises a request that a managementfunctionality be performed. In various embodiments, the indication isreceived from a user, a user system, an application, a contentmanagement application, and/or a system administrator. In someembodiments, the indication is received after a search for content isperformed across multiple content systems and content is selected formanagement from the search results. For example, search for contentrelated to a law suit across an entire company's content systems locatescontent that is required to be disclosed and/or preserved; the contentis selected and managed (retained, indexed, made unchangeable) by thecentral content system during the law suit. In 302, for each of the oneor more external content items a reference object is created thatrepresents the external content item. In some embodiments, the referenceobject is stored in the metadata in a meta-catalog. In some embodiments,the reference object provides the necessary information for the contentmanagement system to access the corresponding content in a legacycontent system.

FIG. 4 is a flow diagram illustrating an embodiment of a process forvirtual repository management. In the example shown, in 400 adesignation is received that an external body of content is to be takenunder management. In various embodiments, the designation is receivedfrom a user, a user system, an application, a content managementapplication, and/or a system administrator. In 402, a reference objectis created for each external item of content in the external body ofcontent. In some embodiments, a crawler is used to locate and selecteach item of content included in the external body of content. Invarious embodiments, the reference object includes metadata allowingaccess to and manipulation of the content that is referred to by thereference object. In some embodiments, the process of FIG. 4 is used tobring entire sets and/or bodies of external content items, e.g., all ora designated subset of content items in an external repository, undervirtual management, such that content management functions are availablecentrally with respect to the external items.

FIG. 5 is a flow diagram illustrating an embodiment of a process forvirtual repository management. In some embodiments, the process of FIG.5 is used to bring external content items under virtual management asthe need/desire arises to perform a content management functioncentrally with respect to one or more particular external content items.In some embodiments, the process of FIG. 5 is used instead of and/or inaddition to the process of FIG. 4. In the example shown, in 500 items ofinterest are found. In various embodiments, items of interest are foundas a result of one or more searches in one or more repositories, itemsof interest are located by performing a full text search on a full textindex of information in one or more repositories, and/or items ofinterest are located by performing a search on crawler results of one ormore repositories. In 502, a request to perform an operation regardingone or more items of interest is received and processed. In someembodiments, at least a subset of the items of interest may be stored inan external repository and in 502 a reference object is created for anyone or more of the items of interest that is/are stored in an externalrepository, if any, and then the operation is performed regarding theone or more items of interest.

FIG. 6 is a flow diagram illustrating an embodiment of a process forfinding objects of interest for virtual repository management. In someembodiments, the process of FIG. 6 is used to implement 500 in FIG. 5.In the example shown, in 600, a search query is received. In 602, asearch is performed across repositories. In some embodiments, therepositories searched include one or more legacy and/or other externalcontent systems. In some embodiments, the search requires translating asearch command or series of commands to a command or series of commandsappropriate for a given legacy content system. In 604, search resultsare received, consolidated, and normalized. In some embodiments, thesearch results require normalization processing in order to format andchange syntax so as to be useable by the content management system usedto perform the search across repositories. In 606, the search resultsare returned. In some embodiments, the search results are returned to anapplication associated with a content management system used to performthe search.

FIG. 7 is a flow diagram illustrating an embodiment of a process forvirtual repository management. In some embodiments, the process of FIG.7 is used to implement 502 in FIG. 5. In the example shown, in 700, arequest is received to perform an operation with respect to one or moreitems. In some embodiments, the one or more items are associated withone or more legacy content systems. In 702, a reference object iscreated for each external content item, if any, associated with therequest received at 700. In some embodiments, the reference objectcomprises information that is stored in a structure in a database thatenables the content management system, its applications, and itsframework to manipulate, access, and perform operations with respect tothe external item of content referred to by the reference object. Insome embodiments, the reference object allows operations to be performedwith respect to the associated external item of content to the sameextent as if the content had been originally created within or ingestedinto the content management system. In 704, the requested operation isperformed.

FIG. 8 is a flow diagram illustrating an embodiment of a process forperforming an operation with respect to content stored in an externalrepository under virtual management. In some embodiments, the process inFIG. 8 is used to implement 704 of FIG. 7 with respect to content storedin an external repository. In the example shown, in 800 a request isissued to perform an operation. In some embodiments, the request isissued by an application or by or through a content management frameworkservice or utility to perform the operation. In 802, the request istranslated to perform the operation. In some embodiments, an adaptertranslates the request to perform the operation. In various embodiments,an adapter is used for one type of legacy content system, a series oflegacy content systems, systems with similar translation requirements,and/or all types of legacy content systems. In 804, the translatedrequest to perform the operation is transmitted. In 806, confirmation isreceived that the operation was performed. In some embodiments, theoperation also returns some information in addition to a confirmation.In 808, the confirmation message is normalized. In some embodiments,normalization comprises processing or formatting in order forappropriate utilization of the information by the content managementsystem. In some embodiments, the additional returned information isnormalized.

Although the foregoing embodiments have been described in some detailfor purposes of clarity of understanding, the invention is not limitedto the details provided. There are many alternative ways of implementingthe invention. The disclosed embodiments are illustrative and notrestrictive.

What is claimed is:
 1. A system for virtual repository managementcomprising: a processor configured to: store, for an external contentitem, a reference object that represents the external content item in aninternal repository of a content management system; receive a request toperform a content management functionality operation using the referenceobject; and cause the performance of the content managementfunctionality operation on the external content item as if the contentmanagement functionality operation is being performed on a content itemstored in the internal repository; and a memory coupled to the processorand configured to provide the processor with instructions.
 2. A systemas in claim 1, wherein the request is received at a content managementsystem.
 3. A system as in claim 1, wherein the request is received froma user.
 4. A system as in claim 1, wherein the request is received froman application.
 5. A system as in claim 1, wherein the contentmanagement functionality operation comprises an operation associatedwith one or more of the following: process automation, library services,repository services, and core content services.
 6. A system as in claim1, wherein the external content item is associated with a legacy contentsystem.
 7. A system as in claim 1, wherein the reference object is partof a meta-catalog of managed content objects.
 8. A system as in claim 1,wherein causing the performance of the content management functionalityoperation comprises issuing to an external repository in which theexternal content item is stored a request that the external repositoryperform with respect to the external content item an operation requiredto achieve the content management functionality operation with respectto the external content item.
 9. A system as in claim 8, wherein dataassociated with the reference object associated with the externalcontent item is used to issue the request to the external repository.10. A system as in claim 1, wherein causing the performance of thecontent management functionality operation comprises translating therequest to generate a translated request in a form associated with anexternal repository in which external content item is stored.
 11. Asystem as in claim 10, wherein the translated request is transmitted tothe external repository.
 12. A system as in claim 11, further comprisingreceiving from the external repository a confirmation that thetranslated request was performed.
 13. A system as in claim 1, whereinthe external content item is one of a plurality of external contentitems comprising an external body of content.
 14. A system as in claim1, wherein the external content item is one of a plurality of externalcontent items comprising an external body of content.
 15. A system as inclaim 1, wherein the external item is associated with an externalcontent management system comprising enterprise content managementsystem.
 16. A system as in claim 1, wherein the external item isassociated with an external content management system comprising acustomer relations management system.
 17. A system as in claim 1,wherein the external item is associated with an external contentmanagement system comprising a business process management system.
 18. Asystem as in claim 1, wherein the external item is associated with anexternal content management system comprising an enterprise contentintegration or enterprise application integration system.
 19. A computerprogram product for virtual repository management, the computer programproduct being embodied in a computer readable medium and comprisingcomputer instructions for: storing, for an external content item, areference object that represents the external content item in aninternal repository of a content management system; receiving a requestto perform a content management functionality operation using thereference object; and causing the performance of the content managementfunctionality operation on the external content item as if the contentmanagement functionality operation is being performed on a content itemstored in the internal repository.
 20. A method for virtual repositorymanagement comprising: storing, for an external content item, areference object that represents the external content item in aninternal repository of a content management system; receiving a requestto perform a content management functionality operation using thereference object; and causing the performance of the content managementfunctionality operation on the external content item as if the contentmanagement functionality operation is being performed on a content itemstored in the internal repository.